Ensure SoLoader is initialized before attempting to load jscexecutor … #26343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This change fixes the issue "ReactInstanceManagerBuilder.build fails unless SoLoader.init has been called" on Android.
The
ReactInstanceManager
constructor callsinitializeSoLoaderIfNecessary
, so the intent is clearly that things should work without an explicit call toSoLoader.init
on the part of the application.However, with the introduction of Hermes, we have
ReactInstanceManagerBuilder.getDefaultJSExecutorFactory
, which gets called before theReactInstanceManager
constructor. It attempts this:This fails with the following stack trace:
Changelog
[Android] [Fixed] - Don't crash ReactInstanceManagerBuilder.build even if SoLoader has not been explicitly initialized
Test Plan
To demonstrate the defect, remove the call to
SoLoader.init
fromRNTester.onCreate
and run the app.To demonstrate the fix, apply this PR, which does in fact also remove the call to
SoLoader.init